File Lifecycle

RL6 is used in a variety of ways based on the user’s role within the healthcare organization. The ultimate goal is that data flows from the source of the incident, is researched and documented completely, and made available to decision makers through reports and graphs. Once issues have been exposed and researched, appropriate decisions can be made to improve patient safety and satisfaction.

The following diagram displays the lifecycle of a RL6:Risk/RL6:Feedback file:

  1. Incomplete – the file submitter can save an Incomplete version and then finish and submit the file later (Submission Form Buttons).
  2. New
    1. Mobile Submission EventClosedA patient or employee related occurrence which is recorded in paper or electronic format. Once recorded, an event file is reviewed by a file manager who may involve other individuals (e.g. using tasks and follow-ups features) to help investigate and resolve the event. – once the file has been submitted via RL6:Mobile, it goes into the state New. The file must then be changed to the proper file type so a File Manager can “work” the file or assign it to another user (Managing a Mobile-Submitted File).
    2. RL6 application submission – once the file has been submitted (Submitting the File), it goes into the state New. The file manager can now “work” the file or assign it to another user.
  3. In-Progress – once the file has been opened by a file manager, it enters the state In-Progress. During this state, the file manager researches, documents, and manages the file. Follow-up details (Adding a Follow-up Action) are added to document the findings. If necessary, file access can be granted (Modifying a File's Status or Ownership) to users for whom the file does not appear within their scope.
  4. Closed – for some organizations, the end of the file lifecycle is when the file gets closed. Closed files can be reopened, if necessary (Management Form Buttons).
  5. Deleted – file managers may delete files (Management Form Buttons) that are invalid, duplicate reports or do not provide sufficient details. This is a “soft” delete, meaning the file is still in the database and can be undeleted.
  6. Note: When a file is closed or deleted, the user must select from a list of administrator-defined statuses (Changing the File Status).